<%
=begin
apps: airflow, apache, argo-cd, argo-workflows, cassandra, consul, contour-operator, dokuwiki, drupal, etcd, fluentd, geode, ghost, grafana,  harbor, influxdb, jasperreports, jenkins, joomla, jupyterhub, kafka, keycloak, kiam, kong, kubernetes-event-exporter, kubewatch, logstash, magento, mariadb, mediawiki, memcached, minio, moodle, mysql, nats, nginx, nginx-ingress-controller, node, opencart, orangehrm, osclass, owncloud, parse, phabricator, phpbb, phpmyadmin, postgresql, postgresql-ha, prestashop, redis, redis-cluster, redmine, sealed-secrets, solr, sonarqube, spark, spring-cloud-dataflow, suitecrm, testlink, tomcat, wavefront, wavefront-adapter-for-istio, wavefront-prometheus-storage-adapter, wildfly, wordpress, zookeeper
platforms: kubernetes, tanzu-application-catalog
id: deploy_extra_resources
title: Deploy extra resources
category: administration
weight: 80
=end %>

There are cases where it may be necessary to deploy extra objects, such a ConfigMap containing application configuration or an extra deployment with a micro-service used by an application. For these cases, this chart supports adding the full specification of other objects via the *extraDeploy* parameter.
